Summary of Changes

Hello @jezekra1, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the filtering capabilities for provider and provider build entities by introducing a more granular user_owned parameter. This allows users to precisely control the visibility of data, enabling them to view only their own entities, entities not belonging to them, or a comprehensive list of all available entities. The changes span from API endpoints to the service and repository layers, ensuring consistent and flexible data access.

Highlights

• Enhanced User Filtering: Introduced a more flexible user_owned filtering mechanism for providers and provider builds, allowing clients to request entities owned by the current user, entities not owned by the current user, or all entities.
• Repository Updates: Added an exclude_user_id parameter to the list methods in IProviderRepository and IProviderBuildRepository interfaces and their respective SQL implementations to support filtering out user-owned entities.
• Service Layer Logic: Updated ProviderBuildService and ProviderService to interpret the user_owned parameter and pass appropriate user_id or exclude_user_id filters to the repositories, including validation for when user_owned is specified without a user.
• API Endpoint Refinement: Modified the list_provider_builds and list_providers API endpoints to accept user_owned as an optional boolean (bool | None), aligning with the new filtering capabilities.
• New Test Coverage: Added end-to-end tests to test_providers.py to validate the correct behavior of the user_owned filtering for providers across True, False, and None scenarios.